|
Date
|
Topic | Readings due | Individual HW due by start of class | Resources | Team Projects due by Noon |
|
R 10 Jan
|
Introduction |
New Blog Entries of 500+/- words Required before each class
|
|||
|
T 15 Jan
|
Open Source Intro | TOS Chp 1 TOS Chp 2 read resource materials |
1) Create public, professional blog for this course at Blogger or Wordpress 2) Join class Wiki and list your name in lastName- alphabetical order hyperlinked to your blog 3) Register for POSSCON by returning permission form with your attendance dates blog confirmation/report/plans |
wikis blogs planets listservs |
|
| R 17 Jan | NO CLASS | SD Preface and Chp 1 | Research and choose 3 open-source projects you would like to participate in (prefereably H/FOSS). Projects should be mature with online communities that welcome newcomers. I can veto projects. Rank them. We will assemble teams based on these rankings.
Blog SubTitle = "My FOSS Preferences" |
fyi: 10 New Open Source Projects | |
|
T 22 Jan
|
Choose Teams and plan team projects
|
The Cathedral and the Bazaar | TOS Exercise 2.4.4 Blog SubTitle = "FOSS Experiences and Reflections" |
in class exercise: Team Intro team details by hand |
|
| R 24 Jan | Open Source Issues | 1) Select an IRC client and join the channel for your Team project; peruse the history and listen to current traffic; blog about your experiences XTRA: REGISTER FOR POSSCON per IN-CLASS INSTRUCTIONS- blog Blog SubTitle = "Joining the Project" |
IRC Tutorial IRC HowTo |
Get organized. Create Team wiki (using 'protected permission' and list team and wiki on class Wiki | |
|
T 29 Jan
|
Team Reports Get and build the Code |
blog about experiences Blog SubTitle = "Subversion Under Control" |
1) Publish a full report on your selected project, its members, history, etc. on the team wiki 2) Publish your ideas for contributing to this project including : select and describe one bug; find the bug in the code; describe how you will fix and test the bug; publish report 3) Download project code |
||
| R 31 Jan | Getting the Code | TOS Chp 5 |
Do Freeciv example in Chapter 5 Explore http://opensource.com/ Blog SubTitle = "Reflections on Open Source in Today's World" |
||
| T 05 Feb | Engaging ! Team Reports |
Blog SubTitle = "Bug Juice" | 1) Choose a bug or set of bugs or an improvement or set of improvements that your team will focus on for the rest of the semester and which you will officially submit to your chosen project; publish report
|
||
| R 07 Feb | Testing and Debugging the Code | TOS Chp 6 |
Do exercises in 6.4, 6.5, 6.6, 6.7; blog experience report Blog SubTitle = "This bugs me" |
||
| T 12 Feb | Testing and Debugging the Code Team Reports |
blog experience report Blog SubTitle = "Squashed?" |
Fix a bug and submit your fix to the project; publish report |
||
| R 14 Feb | Fixing the Code |
chosen article |
Do exercises in 7.2.2, 7.8, 7.9; blog experience report blog your reflections on the article you chose from Software or CoACM magazines Blog SubTitle = "What's Happening?" |
||
| T 19 Feb | Alumni Symposium | Register here | blog Blog SubTitle = "That could be me in x years!" |
Publish your progress relative to your planned timeline. | |
| R 21 Feb | Software Architecture | SD Chp 4 SD Chp 5.4, 5.5, 5.6 |
SD Exercises 5.7, 5.8 (requires planning and getting software example); blog experience report Blog SubTitle = "Refactoring Mindset" |
||
| T 26 Feb | Fixing the Code Team Reports |
blog experience report Blog SubTitle = "Reflections on my Progess" |
Publish your progress and what you plan to have done for 12 March, which is the class Tuesday (after break!!) |
||
| R 28 Feb | TEST #1 | ||||
| T 05 Mar | S P R I N G B R E A K | ||||
| R 07 Mar | |||||
| T 12 Mar | Team Reports |
blog experience report Blog SubTitle = "After the break ..." |
Publish your progress relative to your planned timeline. |
||
| R 14 Mar | Explaining the Code |
SD Chp 6 |
Do exercises in 8.1.1, 8.4; blog experience report Blog SubTitle = "The Doc is in!" |
||
| T 19 Mar | Release early, often | TOS Chp 9 | blog experience report Blog SubTitle = "Release early and often" |
Publish your progress relative to your planned timeline. | |
| R 21 Mar | Team Reports and supervised work | Select 3 presenters from the POSSCON schedule for the day(s) you will attend. Your goal is to meet them and ask them some prepared as well as impromptu questions; Blog your plans ahead of your visit and then plan to blog about your experiences; There are several coffee breaks and a lunch each day at which you can approach your subjects !! Blog SubTitle = "Preparing for POSSCON" |
|||
| T 26 Mar | SD Chp 7 | Blog SubTitle = "Reflections on my progress and plans" | Publish your progress relative to your planned timeline. | ||
| W 27 Mar | POSSCON
|
||||
| R 28 Mar | |||||
| T 02 Apr | SD Chp 8 | Blog SubTitle = "POSSCON Report" | |||
| R 04 Apr | Team Reports | Publish your progress relative to your planned timeline. | |||
| T 09 Apr | Do exercises SD 6.1 - 6.4; | Blog SubTitle = "Chapter 6" | |||
| R 11 Apr | Team Reports | Publish your progress relative to your planned timeline. | |||
| F 12 Apr | SSM Poster Session Submission Deadline 11:59 PM | ||||
| T 16 Apr | Do exercises SD 7.1 - 7.3; | Blog SubTitle = "Chapter 7" | |||
| R 18 Apr | School of Sciences and Mathematics Research Poster Session 11:30am – 1:30 pm at TD Arena | Author Information | |||
| T 23 Apr | Team Reports | Create a PDF from your blog and email it to Dr. Bowring by 8 AM: [lastName]_462_2013_blog.pdf Turn in team self-evaluations by hand. |
Publish your progress relative to your planned timeline. | ||
| R 02 May | Team presentations in room 202 Tate Center --------> 8AM - 11AM >> be sure to check out equipment before the event! Final Presentation Notes: |
RE-Submit your presentation materials (if they have changed) as [TeamName]_present.[type] by NOON | |||